Compare Page

Ease of data access

Characteristic Name: Ease of data access
Dimension: Availability and Accessability
Description: Data should be easily accessible in a form that is suitable for its intended use.
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to lack of ease in data access
The number of complaints received due to lack of ease in data access

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Routinely accessed information to continue operations, should be automatically delivered to stakeholders online without wasting their time to search for it. (1) Daily exchange rates are linked into the accounting application or maintained in a dash board on the accountants desktop.

(2) Production efficiency is made available on a display board in the production floor.

Information needed for management reporting purposes should be identified and catered through built in reports where the users do not have to create the reports themselves. (1) Order status is frequently searched information by different stake holder groups and hence a report is made available with multiple searching criteria.
Facilitate users by providing tools to query the database without using any specific technical knowledge and perform business analytics to bring innovation (1) Technical infrastructure supports the users to develop their own reports based on dynamic information needs without consulting technical staff.
Facilitate the user to filter the relevant information depending on the need. (1) Sales report with filtering criteria for customer and date range.
The interfaces and reports should be created conveniently the users do not have to write complex queries or further process information before usage. (1) Product prices are ordered as per "Relevance" or "Price" to enable an e-commerce customer on a purchase decision

Validation Metric:

How mature is the process of maintaining ease in data access

These are examples of how the characteristic might occur in a database.

Example: Source:
Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact). J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
Accessibility refers to the physical conditions in which users can obtain data Clarity refers to the data’s information environment including appropriate metadata. LYON, M. 2008. Assessing Data Quality ,
Monetary and Financial Statistics.
Bank of England. http://www.bankofengland.co.uk/
statistics/Documents/ms/articles/art1mar08.pdf.
Speed and ease of locating and obtaining an information object relative to a particular activity STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.
Data are available or easily or quickly retrieved. WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.

 

Redundancy

Characteristic Name: Redundancy
Dimension: Consistency
Description: The data is recorded in exactly one place
Granularity: Record
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The volume of redundant data as a percentage to total data

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Maintain the database schema eliminating the causes for redundancies of entities and attributes (1) All customers are in customer table
Ensure that there are no redundant records across distributed databases (1) Organisation has different customer bases maintained in different databases. But one customer is available only in one database
Ensure that same entity is not originally captured more than once in the systems (1) Medical Insurance system refers employee bank details from the payroll.
Ensure that there are no temporary table backups are available in the database (1) Created a backup for employees as employee_temp for a specific purpose and it is still in the database

Validation Metric:

How mature is the creation and implementation of the DQ rules to eliminate the occurrence of redundant data

These are examples of how the characteristic might occur in a database.

Example: Source:
A school has 120 current students and 380 former students (i.e. 500 in total) however; the Student database shows 520 different student records. This could include Fred Smith and Freddy Smith as separate records, despite there only being one student at the school named Fred Smith. This indicates a uniqueness of 500/520 x 100 = 96.2% N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of unwanted duplication existing within or across systems for a particular field, record, or data set. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
There is only one record in a given data store that represents a Single Real-World Object or Event. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Determines the extent to which the columns are not repeated. G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc.